home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 21
/
Aminet 21 (1997)(GTI - Schatztruhe)[!][Oct 1997].iso
/
Aminet
/
comm
/
bbs
/
Cit_Util_7H21.lha
/
Citadel_reset_net.lha
/
reset_net.doc
< prev
Wrap
Text File
|
1997-07-27
|
2KB
|
37 lines
RESET_NET
Due to a bug in CONFG, when you reset the message base, it is not
going into the net nodes file and reseting the last netted message
base. I have created a small tool to fix this problem. It should
be ran as soon after the problem is discovered as possible since a
side effect is that *EVERY* room will be reset and net all its messages
to *EVERY* system. This will probably create a few vortexes which
will go away after the first net session.
reset_net [reset]
If ran with no parameter, it will display all the room/node info
about last message netted. This is a bit different than what shows
in the sysop menu(which is the basis of the problem) because Citadel
keeps a duplicate set of information(not sure why). Because the
duplicate is incorrect, Citadel does not net the messages(even though
they are new).
If the parameter "reset" is included on the command line, the values
will be reset to zero. Use this to fix the problem. Eventually,
Citadel CONFG will include this code and this utility will not be needed.
Note: you should only run this utility if the following situation occurs:
1) You *KNOW* for a fact that your system is recieving messages as
new and is not sending them on to other system.
2) You have not changes the backbone settings and other things that
might cause the problem...
Make sure you warn your net partners that a flood of messages is comming...
After this is ran, the next net session will send *ALL* messages in a room
as new. If you have already netted these messages, the vortex detector
should complain on the recieving systems.